home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
tsql
/
doc
/
tsql.mail
/
000058_kalua@cs.indiana.edu _Wed Mar 31 16:37:46 1993.msg
< prev
next >
Wrap
Text File
|
1996-01-31
|
1KB
|
34 lines
Message-Id: <199303312137.AA15425@optima.cs.arizona.edu>
Received: from moose.cs.indiana.edu by optima.cs.arizona.edu (5.65c/15) via SMTP
id AA15425; Wed, 31 Mar 1993 14:37:51 MST
Received: by moose.cs.indiana.edu
(5.65c/9.4jsm) id AA14305; Wed, 31 Mar 1993 16:37:47 -0500
From: "Patrick P Kalua" <kalua@cs.indiana.edu>
Subject: Re: multi-valued attributes
To: rts@cs.arizona.edu (Rick Snodgrass)
Date: Wed, 31 Mar 1993 16:37:46 -0500 (EST)
Cc: tsql@cs.arizona.edu
In-Reply-To: <199303312122.AA11487@boojum.cs.arizona.edu> from "Rick Snodgrass" at Mar 31, 93 02:22:22 pm
X-Mailer: ELM [version 2.4 PL21]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 490
>
> The proposed schema is much improved over previous ones, but now isn't
> even in 3NF, which is somewhat embarrassing! I suggest that we split
> off the Skills attribute to a new relation:
>
> Skills (Name, Skill)
>
> for which Skill would be a multi-valued attribute, in the
> conventional, snapshot sense. This change would, I think, result in
> BNCF for all relations.
>
> -- Rick
>
It makes more sense. At least let us start with good design principles.
Patrick